Add Agentic Audience Adapter RTD Module

Description

This PR adds a new RTD (Real-Time Data) provider module that injects Agentic Audiences (vector-based) signals into the OpenRTB bid request. Output follows the OpenRTB community extension Agentic Audiences in OpenRTB. Background: IABTechLab Agentic Audiences.

The module reads agentic audience data from browser storage (localStorage or cookie) and injects it into user.data with standard Segment objects (id, name, ext).

Features

• Multi-provider support, no per-provider Prebid modules: Configure any number of vendors under params.providers. Each key (e.g. liveramp, raptive, or a label for a partner not represented by its own Prebid module) becomes user.data[].name for that provider’s segments. No extra Prebid.js modules per provider—only this RTD submodule, plus a storageKey per entry. Future or custom providers work whenever their script stores the Storage Format blob at that key.
• Configuration: If params.providers is missing, empty, or not an object, init returns false and no data is injected.
• OpenRTB-aligned segments: Each stored entry is copied into Segment with Agentic Audiences fields in ext (ver, vector, dimension, model, type); the module does not validate or normalize those values
• Base64 storage: Wrapper JSON in cookie/localStorage is read via atob + JSON.parse as in Storage Format

Configuration

pbjs.setConfig({
  realTimeData: {
    auctionDelay: 300,
    dataProviders: [{
      name: 'agenticAudience',
      waitForIt: true,
      params: {
        providers: {
          liveramp: { storageKey: '_lr_agentic_audiences_' },
          raptive: { storageKey: '_raptive_agentic_audiences_' }
        }
      }
    }]
  }
});

Module params (this submodule)

These are the fields under realTimeData.dataProviders[].params when name is agenticAudience. Other dataProvider options (e.g. waitForIt) are generic RTD behavior, not read by this module.

Each value in providers is an object. Only the following property is read:

Provider keys are arbitrary strings chosen by the publisher (or convention with a data partner). There is no whitelist in the module: a key for a future vendor is valid as long as you point storageKey at where that partner’s script stores data, using the same JSON shape as in Storage Format.

Storage Format

The outer stored value is base64-encoded JSON with an entries array. Each entry maps to one OpenRTB Segment. Description column text is from the OpenRTB community extension Agentic Audiences in OpenRTB (Data.segment and Segment.ext).

OpenRTB Output

Per Agentic Audiences in OpenRTB, the module appends one Data object under user.data for each configured provider that has at least one mappable segment after reading storage.

Single provider

Each Data object’s name is the provider key from params.providers (e.g. liveramp). segment is built from that provider’s stored entries array.

{
  "user": {
    "data": [
      {
        "name": "liveramp",
        "segment": [
          {
            "id": "agentic-audiences",
            "ext": {
              "ver": "1.0.0",
              "vector": "<Base64 Float32 little-endian per spec>",
              "dimension": 3,
              "model": "sbert-mini-ctx-001",
              "type": [1, 2]
            }
          }
        ]
      }
    ]
  }
}

Multiple providers

With several providers (e.g. liveramp and raptive), each reads its own storageKey; user.data contains one element per provider that returned segments, in iteration order of Object.keys(params.providers) (insertion order for ordinary objects).

{
  "user": {
    "data": [
      {
        "name": "liveramp",
        "segment": [
          {
            "id": "agentic-audiences",
            "ext": {
              "ver": "1.0.0",
              "vector": "<Base64 from liveramp storage>",
              "dimension": 384,
              "model": "sbert-mini-ctx-001",
              "type": [1]
            }
          }
        ]
      },
      {
        "name": "raptive",
        "segment": [
          {
            "id": "agentic-audiences",
            "ext": {
              "ver": "1.0.0",
              "vector": "<Base64 from raptive storage>",
              "dimension": 256,
              "model": "raptive-embed-v1",
              "type": [2]
            }
          }
        ]
      }
    ]
  }
}

The sample id values above mirror a typical stored entry; segment id and name are copied from storage as provided (the examples omit name on the segment only for brevity).

The vector in each ext is whatever string was stored per entry (OpenRTB Base64 Float32 LE per spec); this module does not encode or decode it.

Files Changed

• modules/agenticAudienceAdapter.js - RTD submodule implementation
• test/spec/modules/agenticAudienceAdapter_spec.js - Unit tests

Build

gulp build --modules="rtdModule,agenticAudienceAdapter,..."

Testing

npm test -- --file "test/spec/modules/agenticAudienceAdapter_spec.js"

References

• Agentic Audiences in OpenRTB (IAB)
• IABTechLab Agentic Audiences